Image is missing a text equivalent (either an alt="X" or longdesc="X"). Consider brief alternative text that describes the information that the image conveys. You can use the picture properties dialog to add alternative text.
Image is missing a text equivalent (either an alt="X" or longdesc="X").
</xp:variable>
<xp:variable name="str1_1_AttributeTooLong">
Consider alternative text containing fewer words. A long description may be needed if essential information is not available elsewhere on the page. If you don't have a Web page containing this information, you'll need to create one in this Web site and link to it.
Consider alternative text containing fewer words or adding a long description.
</xp:variable>
<xp:variable name="str1_1_AltHasBytesDesc">
This <<xp:value-of select="parent::node()"/>> tag's alternative text may not be valid. Does it accurately describe the information that the image conveys? Consider an informative alternative text and removing the word "bytes".
This alternative text may not be valid. Does it accurately describe the information that the image conveys? Consider an informative alternative text and removing the file extension.
This alternative text may not be valid. Does it accurately describe the information conveyed by the image?
</xp:variable>
<xp:variable name="str1_1_InvalidDesc_Summary">
This alternative text may not be valid.
</xp:variable>
<xp:variable name="str1_1_MissingAlt">
Image is missing a text equivalent (alt="X"). Consider brief alternative text that describes the information that the image conveys. You can use the picture properties dialog to add alternative text.
This APPLET element is missing a text equivalent. Consider brief alternative text that describes the information that the APPLET element conveys as well as a text equivalent in the content of the APPLET element. This enables accessibility for browsers which only handle one of the two forms.
If you use ASCII art, be sure to include alternate equivalent text, using <abbr> with the "title" attribute. Also provide a link to skip over the ASCII figure.
Synchronize descriptions with time-based multimedia tracks.
</xp:variable>
<xp:variable name="Checkpoint2_1">
WCAG 2.1
</xp:variable>
<xp:variable name="str2_1_ColorCoding">
Be sure not to convey information using color alone. Use context or markup as well.
</xp:variable>
<xp:variable name="str2_1_ColorCoding_Summary">
Be sure not to convey information using color alone.
</xp:variable>
<xp:variable name="Checkpoint2_2">
WCAG 2.2
</xp:variable>
<xp:variable name="str2_2_ColorContrast">
Be sure that foreground and background colors for images provide sufficient contrast for low-vision users and for use with black and white screens.
</xp:variable>
<xp:variable name="str2_2_ColorContrast_Summary">
Provide sufficient contrast for low-vision users.
</xp:variable>
<xp:variable name="Checkpoint3_1">
WCAG 3.1
</xp:variable>
<xp:variable name="str3_1_MarkupNotImages">
Use markup rather than images to convey information where possible. Examples: use MathML to markup mathematical equations; use style sheets to format text and control layout.
There are no defined terms or definitions associated with <dl>. This tag should not be used for formatting. Consider using cascading style sheets instead.
If this is a complex data table containing two or more levels of header rows or columns, identify structural rows. Consider using <thead>, <tfoot> for repetitive headers and footers; <tbody> for grouping rows; <col> and <colgroup> for grouping columns; and label the TABLE elements with "scope", "axis", and "headers".
If this is a complex data table identify structure and groupings.
</xp:variable>
<xp:variable name="Checkpoint5_3">
WCAG 5.3
</xp:variable>
<xp:variable name="str5_3_LinearizeLayoutTable">
If this table is used for layout, make sure it makes sense when linearized. Otherwise, provide a linearized version or use cascading style sheets for structure and positioning.
If this table is used for layout, make sure it makes sense when linearized.
</xp:variable>
<xp:variable name="Checkpoint5_4">
WCAG 5.4
</xp:variable>
<xp:variable name="str5_4_FormatforLayoutTable">
If this table is used for layout, do not use a structural format for visual formatting. For example, do not use <th> to display cell contents as centered and bold.
Be sure this page is usable when programmatic objects are turned off or not supported. If not, provide alternative text that describes the information that the element conveys.
Be sure this page is usable when programmatic objects are not supported.
</xp:variable>
<xp:variable name="Checkpoint6_4">
WCAG 6.4
</xp:variable>
<xp:variable name="str6_4_EventHandlers">
Be sure any event handlers are device-independent. If use of this event handler is required for the essential information or use of this page: consider limiting event handlers to device indpendent handlers such as: "onfocus", "onblur" and "onselect". If you must use device-dependent attributes provide a keyboard alternate, for example for "onmousedown" also specify "onkeydown".
</xp:variable>
<xp:variable name="str6_4_EventHandlers_Summary">
Be sure any event handlers are device-independent.
</xp:variable>
<xp:variable name="Checkpoint6_5">
WCAG 6.5
</xp:variable>
<xp:variable name="str6_5_DynamicContent">
Be sure that dynamic content is accessible, or provide an alternative presentation. For example, if you use <frame>, include a <noframes> option; note also that server-side scripts may be more accessible than client-side scripts.
Be sure that dynamic content is accessible, or provide an alternative.
</xp:variable>
<xp:variable name="Checkpoint7_1">
WCAG 7.1
</xp:variable>
<xp:variable name="str7_1_ScreenFlicker">
Avoid causing screen flicker. Where unavoidable, allow users to control flickering. Four to 59 flashes per second should be avoided as should quick changes from light to dark.
</xp:variable>
<xp:variable name="str7_1_ScreenFlicker_Summary">
Avoid causing screen flicker.
</xp:variable>
<xp:variable name="Checkpoint7_2">
WCAG 7.2
</xp:variable>
<xp:variable name="str7_2_Blink">
Do not use <blink>. Consider alternative ways to add emphasis such as <strong> or <em>; or using cascading style sheet command 'text-decoration: blink' so users can stop the effect by turning off style sheets.
</xp:variable>
<xp:variable name="str7_2_Blink_Summary">
Do not use <blink>.
</xp:variable>
<xp:variable name="Checkpoint7_3">
WCAG 7.3
</xp:variable>
<xp:variable name="str7_3_MovingContent">
Avoid moving content or allow users to control the movement.
</xp:variable>
<xp:variable name="str7_3_MovingContent_Summary">
Avoid moving content or allow users to control the movement.
</xp:variable>
<xp:variable name="Checkpoint7_4">
WCAG 7.4
</xp:variable>
<xp:variable name="str7_4_AutoRefresh">
Do not create automatically refreshing pages.
</xp:variable>
<xp:variable name="str7_4_AutoRefresh_Summary">
Do not create automatically refreshing pages.
</xp:variable>
<xp:variable name="Checkpoint7_5">
WCAG 7.5
</xp:variable>
<xp:variable name="str7_5_ReDirects">
Provide the ability to stop this redirect or configure the server to perform redirects.
Be sure this event handler is device-independent. If use of this event handler is required for the essential information or use of this page: consider limiting event handlers to device indpendent handlers such as: "onfocus", "onblur" and "onselect". If you must use device-dependent attributes provide a keyboard alternate, for example for "onmousedown" also specify "onkeydown". Event handlers that rely on mouse coordinates prevent device indepedence and should not be used.
Allow users to turn off spawned windows. Do not cause pop-ups. Do not change the current window without informing users.
</xp:variable>
<xp:variable name="str10_1_PopUps_Summary">
Do not cause pop-ups.
</xp:variable>
<xp:variable name="Checkpoint10_2">
WCAG 10.2
</xp:variable>
<xp:variable name="str10_2_LabelWithFormControl">
Ensure that implicitly associated labels for form controls are properly positioned. The LABEL element must precede its control on the same line. If using one line for the control and one for the LABEL element, <label> must be in the line preceding its control.
Use the latest W3C technologies. For example, MathML for mathematical equations; HTML, XHTML, XML for structured documents; CSS and XSL to define style sheets; XSLT to create style transformations.
This line contains an element that is deprecated, which means that it might eventually be removed from official HTML specifications. It is recommended to avoid deprecated elements. Some examples of good substitutions are: Use <object> instead of <applet>; use <div> with the "align" attribute instead of <center>; use <ul> instead of <dir> or <menu>.
If you are unable to make an accessible page, create an alternative page that is accessible, provides the same utility and is updated as frequently as the inaccessible page. Note: this should be considered only as a "last resort".
If you are unable to make an accessible page, create an alternative page.
</xp:variable>
<xp:variable name="Checkpoint12_1">
WCAG 12.1
</xp:variable>
<xp:variable name="str12_1_NoTitleAttrib">
Frame is missing descriptive title. <frameset>, <frame>, or <noframes> does not contain descriptive title text. Add a descriptive title (title="X"). You can also use the Frames Properties dialog to add a title.
Frame title is empty. <frameset>, <frame>, or <noframes> should contain descriptive title text. Add a descriptive title (title="X"). You can also use the Frames Properties dialog to add a title.
<noframes> should include a link to an alternative page describing the FRAMESET content.
</xp:variable>
<xp:variable name="Checkpoint12_3">
WCAG 12.3
</xp:variable>
<xp:variable name="str12_3_FormNoFieldset">
Large blocks of information should be grouped so they are more manageable. If this form is large consider breaking it up using <legend> and <fieldset>.
Large blocks of information should be grouped so they are more manageable. If this form is large consider describing your <fieldset> groupings using <legend>.
Large blocks of information should be grouped so they are more manageable.
</xp:variable>
<xp:variable name="str12_3_TableandNoCaption">
Large blocks of information should be grouped so they are more manageable. If this is a large data table consider describing its content using <caption>.
Web sites and pages should provide semantic information and orientation. Using good meta data can provide orientation information about the site to the user. Helpful tags: <title>, <address>, <meta>, <!doctype>, <link>. Use <ol>, <ul> and cascading style sheets to provide contextual clues in lists. Provide navigation bars, site maps and search features to assist as well.
If this page requires an applet, plug-in or other application on the client in order to convey important information, be sure you provide a link to a fully accessible plug-in or applet.